The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Mar 4, 2026 6:09am

@cursor review

@greptile

Greptile Summary

This PR fixes cursor jumping to the end of react-simple-code-editor instances after selecting a <tag> or {{env-var}} from a dropdown. The fix inverts the responsibility for cursor-position computation: instead of having the consumer (handler in code.tsx, condition-input.tsx, use-subflow-editor.ts) attempt to re-derive the cursor position by searching for delimiters in the post-insertion DOM value, the producer (the dropdown's selection handler) now pre-computes the exact target offset and passes it as a second argument to onSelect. A new shared utility restoreCursorAfterInsertion wraps the setTimeout(0) + selectionStart/selectionEnd pattern so React's controlled-component commit can flush before the cursor is moved.

Key changes:

• utils.ts — New restoreCursorAfterInsertion(textarea, newCursorPosition) utility replaces the previous multi-file, delimiter-scanning cursor restoration logic.
• tag-dropdown.tsx — Computes newCursorPos = insertStart + 1 + processedTag.length + 1 (position immediately after the closing >) and passes it via the updated onSelect signature.
• env-var-dropdown.tsx — Computes tagLength = 2 + envVar.length + 2 (length of {{envVar}}) and passes the correct absolute position via onSelect. Also removes a duplicate dead if/else where both branches were identical.
• code.tsx, condition-input.tsx, use-subflow-editor.ts — Updated to forward the pre-computed cursor position and call restoreCursorAfterInsertion. CSS.escape is now applied to blockId in condition-input.tsx's querySelector, addressing a latent selector injection risk.
• One minor documentation inaccuracy: the JSDoc in utils.ts calls setTimeout(0) a "microtask" when it is actually a macrotask (the distinction is intentional and correct, just misdocumented).

Confidence Score: 4/5

• This PR is safe to merge — the fix is well-scoped, the cursor math is correct in all code paths, and the approach is simpler and more reliable than the previous delimiter-scanning strategy.
• The pre-computed cursor position is verifiably correct for all tag and env-var insertion cases (both when a partial trigger exists and when inserting from scratch). The shared utility is minimal and handles null gracefully. The only finding is a minor JSDoc inaccuracy ("microtask" vs "macrotask") that has no runtime impact. No tests were added, but the change is straightforward enough that manual testing is reasonable.
• No files require special attention.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant User
    participant Dropdown as TagDropdown / EnvVarDropdown
    participant Handler as handleTagSelect / handleEnvVarSelect
    participant React as React (setState)
    participant Utils as restoreCursorAfterInsertion
    participant DOM as Textarea DOM

    User->>Dropdown: Clicks / presses Enter on item
    Dropdown->>Dropdown: Compute newValue & newCursorPos<br/>(insertStart + tag length)
    Dropdown->>Handler: onSelect(newValue, newCursorPos)
    Handler->>React: setState / setCode(newValue)
    Handler->>Utils: restoreCursorAfterInsertion(textarea, newCursorPos)
    Note over Utils: setTimeout(0) — macrotask
    React-->>DOM: Re-render commits new value
    Utils->>DOM: textarea.focus()<br/>selectionStart = newCursorPos<br/>selectionEnd = newCursorPos
    DOM-->>User: Cursor at correct position

_{Last reviewed commit: a73bd6c}

@greptile

@cursor review

@greptile

@cursor review

@greptile

@greptile

@greptile

@cursor review

@greptile

@cursor review